Skip to content
This repository has been archived by the owner on Apr 15, 2019. It is now read-only.

Make sure confirmations are updated - Closes #716 #735

Merged
merged 11 commits into from
Sep 14, 2017

Conversation

slaweet
Copy link
Contributor

@slaweet slaweet commented Sep 12, 2017

This became a bigger issue than it looked at the beginning. For explanations of all changes see individual commit messages.
Closes #716

because they have higher "confirmations" field
if the app is not in background, because we want to show updated
number of "confirmations"
because we need to update "confirmations" number
... because transactions table was slow when it was re-rendering all
rows.
Format it with 'k', e.g. 1k instead of 1324, 23k instead of 23456
so that we don't have to re-render too often.
@slaweet slaweet force-pushed the 716-confirmations-not-updated branch from b49812d to 6d5e7a8 Compare September 14, 2017 08:06
reyraa
reyraa previously approved these changes Sep 14, 2017
@slaweet slaweet merged commit 1e6e03b into development Sep 14, 2017
@slaweet slaweet deleted the 716-confirmations-not-updated branch September 14, 2017 09:32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants